Release 10.1A: OpenEdge Getting Started:
Installation and Configuration

Reviewing the UNIX system installation directory structure

The OpenEdge installation PATH contains configuration files and several subdirectories. The installation PATH directory contains the OpenEdge executables, several procedure (.p) files, and other related files and subdirectories. During installation, the $DLC environment variable is automatically set to your OpenEdge installation PATH.

Note that the $DLC variable is set in the various command scripts; the variable is not set at the system level.

Table 3–7 describes a directory tree of the OpenEdge subdirectories.

Table 3–7: OpenEdge ($DLC) directory structure

Directory name	Description
bin	Contains the executable files for OpenEdge, such as PRODB. It also contains batch files and system executables.
certs	Contains the public keys of the Certificate Authorities (CAs) used by OpenEdge clients to perform server-side certificate validation when communicating with secure Web servers using HTTPS.
esbadapter	Contains the configuration and support code for the OpenEdge Adapter for Sonic ESB.
include	Contains the header files required for ESQL.
install	Contains Java tailoring classes that only the Installation Utility uses.
java	Includes the Java files and executables necessary for running OpenEdge products.
javahelp	Contains .jar files for the OpenEdge Application Debugger.
jdk	Contains the Java Development Kit files and executables necessary for running OpenEdge products.
jms	Contains files to support client deployment of java messaging.
jre	Contains the Java Run-time Environment files and executables necessary for running OpenEdge products.
keys	contains encrypted RSA Private Key and Certificate file information.
lib	Contains shared objects necessary for running OpenEdge executables.
licenses	Contains license and copyright information related to HTTP Client, OpenSSL toolkit, Perl, and w3c IPR software notice.
odbc	Includes files to support ODBC.
oebuild	Includes files that theOpenEdge MAKE utility uses when creating custom executables.
ora	Contains files to support the DataServer for ORACLE.
perl	Contains files to support the use of the Perl scripting language.
proedit	Contains files to support the advanced editing features.
prohelp	Includes the online help and other necessary files for OpenEdge.
prolang	Contains the national language support directories.
properties	Contains property files that manage the configuration of OpenEdge services, such as WebSpeed, the NameServer, and the AppServer.
scripts	Can contain files related to the Failover Cluster component.
servlets	Identifies the default location of the AppServer Internet Adapter (AIA) and Web Services Adapter (WSA) servlet containers. These containers include Web definitions.1
sonic	Contains files that support the Sonic client and container.
sports	Includes the schema triggers and supplier information for each sample database.
sports2000trgs	Includes the schema triggers for the Sports2000 database.
src	Contains source files for OpenEdge ADE tools, such as the Data Dictionary, Procedure Editor, and Sample Applications.
templates	Can contain files related to the Failover Cluster component.
toolkit	Includes files that help in deploying and encrypting your applications.
tty	Includes mostly object (.r) files and r-code procedure libraries (.pl) for character-mode OpenEdge.
ubqmanager	Includes files used by the AppServer exclusively. Do not modify these files.
webspeed	Includes static files for the WebSpeed Workshop, WebTools, and HTML help that reside on the Web server.

1Refer to your OpenEdge product documentation for details about configuring AIA and WAS.